Mobile Internet Protocol (IP) Location

ABSTRACT

A mobile IP location server that retrieves the location of a mobile device based on the public IP address that a mobile device is using. A mobile IP location server comprises a mobile location protocol interface, an identifier resolver, and a location manager. The mobile location protocol interface interacts with location applications and receives and responds to location requests. The identifier resolver converts a device&#39;s public IP address to a real mobile identifier (e.g. MSISDN) and performs address conversion by either interacting with an HTTP proxy server or querying a network address translation (NAT) table. The location manager retrieves the location of a mobile device given the device&#39;s real mobile identifier (e.g. MSISDN). A web application requests mobile IP location services by transmitting an IP request to the mobile IP location server. An IP location request contains a mobile device&#39;s public IP address, port number, and any application specific information.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/750,056, filed 25 Jun. 2015; which is a continuation of U.S. Ser. No.14/198,027, filed 3 Mar. 2014; which is a continuation of U.S. Ser. No.13/402,406, filed 22 Feb. 2012; which claims priority of U.S.Provisional Application No. 61/573,086, filed 30 Aug. 2011, entitled:“Mobile Internet Protocol (IP) location,” and U.S. ProvisionalApplication No. 61/457,316, filed 25 Feb. 2011, entitled: “MobileInternet Protocol (IP) location,” the entirety of which are incorporatedherein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to wireless Internet Service Providers(ISPs), and information content delivery services/providers. Moreparticularly, it relates to location services for the wireless industryand Web content providers.

2. Background of Related Art

Computer networks amass a collection of digital devices (e.g. computers,mobile devices, etc.), and cooperate with one another to permitcommunication amongst devices integrated within.

Every device that operates on a computer network is allotted a uniquenumerical identifier. An Internet Protocol address (IP address), forinstance, is a numerical identifier assigned to each device operating ona Transmission Control Protocol/Internet Protocol (TCP/IP) network. AnIP address enables a specific network node (e.g. a computer) to betargeted in a communication session and/or an information transmission.Moreover, an IP address identifies the location of a particular deviceon a network, permitting a communication session and/or an informationtransmission to be routed accurately.

An IP address is either statically or dynamically assigned to a networkdevice.

A dynamically assigned IP address is allocated to a device each time thedevice accesses a network (e.g. each time a computer is booted), and/oreach time an inherent timer has expired. A dynamic IP address is notfixed for any specific network device. Rather, a multitude of variousdynamic IP addresses may be assigned to a host throughout the course ofa network session.

Alternatively, a statically assigned IP address is permanently allocatedto a network node. In particular, a static IP address is configuredmanually in the hardware or software portion of a device and thusprovides a constant source of identification.

Two versions of the Internet Protocol are currently in use: InternetProtocol version 4 (1Pv4) and Internet Protocol version 6 (1Pv6). 1Pv4and 1Pv6 each deploy variant addressing schemes. 1Pv4 addresses are 32bits long, yielding an address space that consists of 21132 unique IPaddresses. Recently, as a result of the monumental growth of theinternet, the supply of unallocated 1Pv4 public IP addresses (i.e.globally unique IP addresses that may be routed on the internet) hasrapidly diminished.

Consequently, Pv6 was developed to broaden the supply of availableaddress space. An 1Pv6 address contains 128 bits, providing 2̂128 uniqueIP addresses, which is enough to provide global unique IP addresses toall digital devices. Yet, the majority of today's network operatorscontinue to use 1Pv4. Thus, several methods have been enacted in anattempt to conserve 1Pv4 address space.

For instance, one address conservation tactic incorporates private IPaddresses. A private IP address is not globally unique and therefore notroutable on the internet. Rather, private IP addresses are reserved forprivate networks, upon which devices primarily communicate and transferinformation amongst other locally connected devices. Devices on aprivate network do not engage in frequent connectivity with outsidenetworks, nor are they directly connected to the internet. Hence, asopposed to a globally unique public IP address, a private IP address isonly required to be unique to devices operating on a common privatenetwork. Therefore, private IP addresses are essentially unique localaddresses, enabling a range of private IP addresses to be reused over amultitude of private networks.

When a device on a private network attempts to access the internet, thedevice's private IP address is first converted to a public IP address.Address conversion masks a requesting device's private IP address,rendering the address undetectable to external network devices. Addressconversion is commonly achieved via Network Address Translation (NAT).

FIG. 4 portrays a conventional network topology incorporating a NetworkAddress Translation (NAT) enabled device. A device 400 with NetworkAddress Translation (NAT) functionality (e.g. a router, a gateway, afirewall, etc.) is situated between a private network 410 and a publicnetwork 420 (e.g. the internet). Private network addresses are notroutable on the internet. Therefore, any device on a private network 410attempting to access a node (e.g. a web server) on a public network 420(e.g., the internet) must first pass communication through a NetworkAddress Translation (NAT) enabled device 400. Network AddressTranslation (NAT) 400 converts a private IP address to a public IPaddress, and vice-versa, by referencing and recording addresstransformations in a Network Address Translation (NAT) table 430.

FIG. 5 portrays a conventional transmission of an IP packet from aprivate network node to a public network node using Network AddressTranslation (NAT). A Network Address Translation (NAT) enabled device isfurnished with a pool of globally unique public IP addresses. In step500, a device with a private IP address transmits an IP packet to adevice (e.g. a web server) operating on a public network. As depicted instep 510, the Network Address Translation (NAT) device on the privatenetwork intercepts the transmitted IP packet. Network AddressTranslation (NAT) then converts the source address in the transmitted IPpacket from a private IP address to a public IP address, selected fromthe Network Address Translation (NAT) mutable address pool, as shown instep 520. In step 530, Network Address Translation (NAT) subsequentlyrecords the new public/private IP address combination in the NetworkAddress Translation (NAT) table for future lookup. The same addressconversion is performed in all subsequent IP packets transmitted acrossthe same line of communication.

FIG. 6 portrays a conventional transmission of an IP packet from apublic network node to a private network node using Network AddressTranslation (NAT).

An IP packet is transmitted from a public network node to a privatenetwork node, as depicted in step 600. The transmitted IP packet issubsequently intercepted by a Network Address Translation (NAT) enableddevice, configured at an entry point on the receiving private network,as shown in step 610. Network Address Translation (NAT) detects thedestination address designated in the received IP packet and queries theNetwork Address Translation (NAT) table for a match in step 620. If amatch is detected (step 630), the public IP address in the packetdestination address field is converted to an affiliated private IPaddress in step 650, as recorded in the Network Address Translation(NAT) table. The packet is thereafter routed to an appropriatedestination device in step 660. In the event that a match is notdiscovered in the Network Address Translation (NAT) table, the packet isdropped (step 640).

A proxy server may alternatively function as a gateway device between aprivate network and a public network.

FIG. 7 depicts a conventional network topology incorporating a proxyserver.

As depicted in FIG. 7, a proxy server 700 is situated between a publicnetwork 720 and a private network 710 (i.e. a proxy server 700 isconfigured at an entry node on a private network 610). A networktopology deploying a proxy server 700 routes allcommunication/information requests transmitted from a private network710 to a public network 720, and vice versa, through the proxy server700.

Similar to Network Address Translation (NAT), a proxy server may shieldthe identity of a device on a private network from being exposed to theinternet. A proxy server is also able to modify received IP packetsbefore forwarding packets to an intended destination. Therefore, a proxyserver may perform address conversion in an IP packet and additionallyappend any relevant application specific information.

The location of a public IP address assigned to a device is currentlyobtainable on the internet via request to a suitable web service. Forinstance, http://www.ip2location.com enables a user to supply an IPaddress in return for location information.

There are numerous situations in which the location of a web clientassociated with a particular internet session would be beneficial to abusiness. For instance, a bank may desire the location of a clientrequesting online banking resources for security purposes (e.g.authentication and/or anti-fraud). IP location services may additionallybe beneficial in law enforcement scenarios and assisting in 911emergency location determination. Moreover, IP location services enablea business to target promotional information to relevant consumers basedon a device's proximity to a particular site of interest. IP locationservices furthermore enable a business to engage in location basedadvertising.

There are companies (e.g. Quova) that provide commercial IP locationservices. However, current IP location services are only applicable towireline networks (e.g. cable or DSL ISP providers) where staticlocation of each individual user can be pre-provisioned.

Unfortunately, location information associated with a public IP addressthat is allocated to a mobile device is not available. Instead, currentIP location services are merely able to provide the identity of aninternet service provider (ISP) that owns an IP address assigned to amobile device. Hence at the moment, it is not possible to locate amobile device based upon the public IP address that a mobile device isusing.

Wireless packet data services are provided by most wireless carriersusing various technologies (e.g. UMTS, LTE, CDMA1×, WiMAX, WiFihotspots, etc.). While smart phones with high processing power and ahigh resolution display are popular, more people are using mobile phonesto access web interfaces via a built-in web browser. Consumers desire anIP location service that is able to provide location information basedupon a mobile device's IP address.

SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, a mobileInternet protocol (IP) location server comprises a mobile locationprotocol interface to receive an Internet protocol (IP) location requestfor location of a given mobile device. An identifier resolver converts apublic Internet protocol (IP) address supplied in the IP locationrequest, to a real mobile identifier of the given mobile device. Alocation manager obtains a geographic location of the given mobiledevice based upon the real mobile identifier of the given mobile device.

A method of providing location for a mobile device in a private networkin accordance with another aspect of the invention comprises receivingan Internet protocol (IP) location request for location of a givenmobile device from a requesting device. An owner of an IP address in theIP location request is determined. A real mobile identifier of the givenmobile device is resolved based on a public IP address of the givenmobile device. Location for the given mobile device is obtained usingthe real mobile identifier, and the obtained location is returned to therequesting device.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the present invention become apparent tothose skilled in the art from the following description with referenceto the drawings, in which:

FIG. 1 portrays an exemplary mobile IP location server, in accordancewith the principles of the present invention.

FIG. 2 illustrates exemplary high level architecture of IP MobileLocation Services in a 3GPP network environment (including the supportof non-3GPP access), in accordance with the principles of the presentinvention.

FIG. 3 illustrates an exemplary mobile IP location service flow using amobile IP location server, in accordance with the principles of thepresent invention.

FIG. 4 portrays a conventional network topology incorporating a NetworkAddress Translation (NAT) enabled device.

FIG. 5 portrays a conventional transmission of an IP packet from aprivate network node to a public network node using Network AddressTranslation (NAT).

FIG. 6 portrays a conventional transmission of an IP packet from apublic network node to a private network node using Network AddressTranslation (NAT).

FIG. 7 depicts a conventional network topology incorporating a proxyserver.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

In accordance with the principles of the present invention, a method andapparatus for acquiring a geographic location for a mobile device, basedon a public IP address that the mobile device is using, comprises amobile IP location server. A web service requests mobile IP locationservices for a particular mobile device by transmitting an IP locationrequest to the mobile IP location server, in accordance with theprinciples of the present invention. An IP location request preferablyincorporates a mobile device's public IP address, a port number overwhich the mobile device is communicating, and an application type forthe requesting web service.

A mobile IP location server is comprised of three functional elements: amobile location protocol (MLP) interface, an identifier resolver, and alocation manager. All requests for location services are transmittedover the mobile location protocol (MLP) interface, in accordance withthe principles of the present invention.

The identifier resolver converts a public IP address supplied in an IPlocation request, to a corresponding device's real mobile identifier,e.g., IMSI, MSISDN, etc. In accordance with the principles of thepresent invention, the identifier resolver performs address conversionby querying either a Network Address Translation (NAT) enabled device oran HTIP proxy server configured on a mobile device's serving network.

In accordance with the principles of the present invention, the locationmanager utilizes existing location services to obtain a geographiclocation for a mobile device, based upon the device's real mobileidentifier.

A mobile IP location server may be used for commercial IP locationservices, wherein city level civic location information is provided,with consideration of subscriber privacy settings. Additionally, amobile IP location server may perform emergency IP location services(e.g. E-911 location determination), in which precise location isprovided with full civic location.

The present invention provides a mobile IP location server thatretrieves the location of a mobile device, based on the public IPaddress that the mobile device is using. A web service requests locationinformation for a particular public IP address by transmitting an IPlocation request to the mobile IP location server, in accordance withthe principles of the present invention.

FIG. 1 portrays an exemplary mobile IP location server, in accordancewith the principles of the present invention.

As depicted in FIG. 1, the mobile IP location server 230 comprises threemain functional elements: a mobile location protocol (MLP) interface110, an identifier resolver 120, and a location manager 130.

The mobile location protocol (MLP) interface 110 accepts all IP locationrequests transmitted to the mobile IP location server 230 and returnsall IP location responses. A web service interacts with the mobilelocation protocol (MLP) interface 110 to request IP location servicesfrom the mobile IP location server 230. The mobile location protocol(MLP) interface 110 additionally interacts with location applications torequest and obtain location information for particular public IPaddresses.

The identifier resolver 120 interworks with network entities, e.g., afirewall, a Hypertext Transfer Protocol (HTIP) proxy server, a servinggateway and/or a Packet Data Network (PDN) gateway to convert a publicIP address received for a mobile device to the device's real mobileidentifier, e.g., IMSI, MSISDN, etc.

The location manager 130 is a location server (e.g. MPC, GMLC, etc.)that determines a mobile device's current geographic location viaconventional mobile location services. A conventional mobile locationservice uses a device's real mobile identifier (e.g. IMSI, MSISDN, etc.)to obtain a geographic location for that device.

A web service requests IP location services by transmitting an IPlocation request to the mobile IP location server 100, in accordancewith the principles of the present invention. In one particularembodiment, a web service may trigger the transmittal of an IP locationrequest to the mobile IP location server 100, each instance the webservice is accessed.

An IP location request preferably contains a mobile device's public IPaddress, the port number over which a mobile device is communicating,and an application type for the requesting web service.

Due to dynamic address allocation, a mobile device may be reassigneddifferent public IP addresses as it moves and re-registers on a network.Moreover, a mobile device's public IP address may be periodicallyreleased on account of idle timeouts. Thus, a public IP address is not aconstant source of identification and may not be used to directlyidentify a specific mobile device.

Moreover, existing control plane location services retrieve locationinformation for a mobile device based on a device's real mobileidentifier (e.g. ISMI, MSISDN, etc.), not a device's public IP address.Therefore, unless a mobile device owns a static public IP address (i.e.,a public IP address that remains constant), the public IP addresssupplied in an IP location request cannot be reliably used to directlyidentify or locate a mobile device.

The inventive mobile IP location server 100 retrieves a mobile device'sreal mobile identifier (e.g. IMSI, MSISDN, etc.) based upon the publicIP address indicated in a received IP location request. The mobile IPlocation server 100 then queries a location service to obtain ageographic location for the relevant mobile device, based on thedevice's retrieved mobile identifier, e.g., IMSI, MSISDN, etc.

FIG. 2 illustrates an exemplary high level architecture of a mobile IPlocation server 230 in a 3GPP network environment (including the supportof non-3GPP access), in accordance with the principles of the presentinvention.

In accordance with the principles of the present invention, a mobiledevice 200 accesses a web service 210, which triggers an IP locationrequest 220 to the mobile IP location server 230. The transmitted IPlocation request 220 20 incorporates the mobile device's 200 public IPaddress, port number, and an application type for the web service 210that transmitted the request 220.

The mobile IP location server 230 interacts with a network addresstranslation enabled device 240 or a proxy server 250 to convert thepublic IP address supplied in the IP location request to thecorresponding device's real mobile identifier, e.g., ISMI, MSISDN, etc.Following address conversion, the mobile IP location server 230initiates a location request to a location server 260 based on themobile identifier (e.g., ISMI, MSISDN, etc.) retrieved for the relevantmobile device 200. Location information for the mobile device 200 isreturned to the mobile IP location server 230 and forwarded to the webservice 210 that initiated the IP location request 220.

FIG. 3 illustrates an exemplary mobile IP location service flow using amobile IP location server, in accordance with the principles of thepresent invention.

In step 300, a mobile device gains access to the Internet via anappropriate internet service provider. Internet service providers (e.g.Verizon Wireless, AT&T, etc.) conventionally administer 1Pv4 dynamicprivate IP addresses to mobile devices. Private IP addresses are notroutable on the Internet. Thus, upon Internet access, the firewall onthe device's serving network converts the device's private IP address toa public IP address, preferably via Network Address Translation (NAT).

In step 310, the mobile device 200 initiates a web service session 210with a web service provider (e.g. an online banking service).

In step 320, the web service 210 that the mobile device 200 is accessingtransmits an IP location request to the mobile IP location server 230,to attain location information for the requesting mobile device 200.

The web service 210 preferably transmits the IP location request 220 tothe mobile IP location server 230 via a Live Communications Server (LCS)Client protocol over the mobile location protocol (MLP) Interface 120.The IP location request 220 preferably includes the mobile device'spublic IP address, port number, and any relevant application specificinformation (e.g. application type).

In step 330, the mobile IP location server 230 receives the transmittedIP location request 220, via the mobile location protocol (MLP)interface 120, and identifies the public IP address that is indicatedwithin. The mobile IP location server 230 then determines the networkoperator that owns the public IP address received in the IP locationrequest 220.

The owner of a public IP address is registered in the public domain.Therefore, the network/operator that an IP address belongs to may bedetermined via a database query to the IP address registry.

In an alternate embodiment, the mobile IP location server 230 maintainsan IP address database for each mobile operator that the mobile IPlocation server 230 is serving. An inherent IP address database permitsfast and accurate address lookup.

In yet another embodiment, a commercial provider company inserts networkoperator information into IP location requests sent to the mobile IPlocation server 230.

In step 340, address conversion is performed to accurately identify themobile device 200 that corresponds to the public IP address indicated inthe received IP location request 220. In particular, the identifierresolver converts the public IP address (e.g. 1Pv4) received for themobile device 200 to a corresponding private IP address or real mobileidentifier, e.g., IMSI, MSISDN, etc. Several mechanisms may be used toachieve this conversion.

One address conversion tactic the identifier resolver 110 may performincorporates Network Address Translation (NAT). With authorization, theidentifier resolver 110 may access a Network Address Translation (NAT)enabled device (e.g. a firewall at the proxy server 250) on the relevantdevice's serving network. The identifier resolver 110 may then initiatea request to query the Network Address Translation (NAT) table for thereal mobile identifier of the mobile device 200, as documented in theNAT binding. The mobile identifier of the mobile device 200 ispreferably returned in one of the following formats: MSISDN, IMSI, MSN,MIN, MON, and/or a private IP address assigned to the mobile device 200.

Alternatively, the identifier resolver 110 may retrieve the mobileidentifier and/or private IP address of the mobile device 200 byinteracting with an HTIP proxy server 250 deployed on the mobiledevice's serving network.

An HTIP proxy server 250 on a network may insert a proprietary header into each IP packet that is routed through the HTIP proxy server 250. Thesupplemental proprietary header may encompass an identifier thatrepresents a transmitted IP packet's originating mobile device 200.However, to preserve user privacy, a device's true mobile identifier(e.g. IMSI, MSISDN, etc.) need not be used. Rather, a proxy server maymaintain a database that maps identifiers inserted in a proprietaryheader to the real mobile identifiers (e.g. IMSI, MSISDN, etc.) they arebeing used to represent.

If this method is available, the identifier in a proprietary headershould also be supplied in an IP location request 220 sent to the mobileIP location server 230. The identifier resolver 110 may then interactwith the HTIP proxy server 250 to query the proxy server's database fora real mobile identifier of the mobile device 200, using the identifiersupplied in a received IP location request 220.

As shown in step 350, address conversion performed by the identifierresolver 110 results in a mobile device's real mobile identifier (e.g.MSISDN, IMSI, MSN, MIN, and/or MON) or a corresponding private IPaddress.

If address conversion yields a private IP address, then the retrievedprivate IP address must be converted to a real mobile identifier (step360) before location services may be applied.

To convert a private IP address to a real mobile identifier (e.g. IMSI,MSISDN, etc.), the identifier resolver 110 determines the servinggateway that owns the relevant private IP address. The identifierresolver 110 may then retrieve the mobile identifier (e.g. IMSI, MSISDN,etc.) and current serving node (e.g. SGSN, MME, etc.) affiliated withthe private IP address, from the serving gateway or Packet Data Network(PON) gateway 242 that is serving the mobile device 200.

The PON gateway 242 may either belong to a mobile operator or reside inan enterprise (e.g. Blackberry™ by Research in Motion uses IP addressesassigned by the enterprise where the RIM server is hosted).

When 1Pv6 is used, a private IP address assigned to a mobile device maybe the same address used to access the internet. Thus, addressconversion is not necessary in an 1Pv6 implementation.

In step 370, once the mobile IP location server 230 retrieves the realmobile identifier of the mobile device 200 and serving node address(optional), the location manager 130 requests the location of the mobiledevice 200 via standard location procedures (e.g. MPG, SUPL SLP, orGMLC). A location request 220 incorporating the real mobile identifierof the mobile device 200 and optional serving node address, istransmitted to the location manager 130 over the mobile locationprotocol (MLP) interface 120.

In step 380, the location manager 130 transmits a geographic locationfor the mobile device 200 to the mobile IP location server 230, over themobile location protocol (MLP) interface 120. The mobile IP locationserver 230 subsequently returns the retrieved location information tothe web service 210 that transmitted the IP location request 220.

It is preferred that the mobile IP location server 230 cache the Iresults of a location request. Caching may be performed by assigning akey to location results to use in location rebids. A cached location maybe configured with a stale age, in accordance with the principles of thepresent invention. Once a cached location expires based on stale age,the cached location is deleted and the expired location key results inerror.

Mobile IP location services may potentially conflict with a subscriber'sprivacy settings. However, despite location privacy configurations, thepresent invention may still perform emergency location services andconventional commercial location requests.

If an emergency IP location request (i.e. EME_LIR) for a mobile devicewith location privacy is transmitted to the mobile IP location server230, the mobile IP location server 230 may override privacyconfigurations. The mobile IP location server 230 may return preciselocation information to the requesting web application 210, along withthe civic location of the serving Cell-ID of the mobile device 200.

Alternatively, if a commercial IP location request 220 for a mobiledevice 200 with location privacy is transmitted to the mobile IPlocation server 230, the mobile IP location server 230 may provide onlycity level location information derived from the serving Cell-ID of themobile device 200.

In an alternate embodiment, the mobile IP location server 230 maytransmit a subscriber privacy notification to the mobile device 200whenever the web service 210 requests location of the mobile device 200via an IP location request 220.

The present invention preferably utilizes existing location services(e.g. 3GPP Control Plane based via GMLC, etc., OMA User Plane based viaSUPL SLP, or MPC for 3GPP2).

The present invention may be used in conjunction with the followingwireless access technology: 3GPP based packet data using GERAN, UTRAN,or E-UTRAN radio access, Wireless LAN based on IEEE 802.11x, WirelessPersonal Area Network Based on IEEE 802.15, Worldwide Interoperabilityfor Microwave Access or Wireless metropolitan area network based on IEEE802.16, 2GPP2 packet data access technologies (e.g. 1×EVDO based),Packet Data Access over Satellite, and high packet data access overspeed point-to-point optical link (e.g. based on 802.17). Moreover, thepresent invention is applicable to other network types (e.g. CDMA2000 1×network).

The present invention has particular applicability to localized webcontent, location orient advertising, local weather applications,automatic product configuration, fraud detection or prevention, userauthentication, law enforcement applications, and digital rightsmanagement (e.g. digital rights of video and/or audio on demand).

While the invention has been described with reference to the exemplaryembodiments thereof, those skilled in the art will be able to makevarious modifications to the described embodiments of the inventionwithout departing from the true spirit and scope of the invention.

1. (canceled)
 2. A mobile Internet Protocol (IP) location server,comprising: a mobile location protocol interface configured to receive arequest for location information for a mobile device; an identifierresolver configured to query a given network node operating on a givennetwork for a mobile identifier that uniquely identifies the mobiledevice based on a public IP address included in the location request;and a location manager configured to query another network nodeoperating on another network for location information for the mobiledevice based on the mobile identifier of the mobile device.
 3. Themobile IP location server of claim 2, wherein the mobile identifiercomprises at least one of an International Mobile Subscriber Identity(IMSI) and a Mobile Station International Subscriber Directory Number(MSISDN).
 4. The mobile IP location server of claim 2, wherein the givennetwork node operating on the given network comprises a network addresstranslation (NAT) gateway.
 5. The mobile IP location server of claim 4,wherein the given network comprises a WiFi network.
 6. The mobile IPlocation server of claim 5, wherein the other network comprises awireless carrier network.
 7. The mobile IP location server of claim 4,wherein the other network comprises at least one of a Long TermEvolution (LTE) network and a 4G network.
 8. The mobile IP locationserver of claim 2, wherein the location information characterizes amunicipal area in which the mobile device is located.
 9. The mobile IPlocation server of claim 2, wherein the given network node operating onthe given network comprises a proxy server for the mobile device. 10.The mobile IP location server of claim 9, wherein the other networkcomprises a wireless carrier network.
 11. A method comprising: receivingan Internet Protocol (IP) location request for geographic locationinformation associated with a mobile device; querying a given networknode for a real mobile identifier corresponding to a public IP addressassigned to the mobile device in response to the IP location request;and querying another network node operating on a long term evolution(LTE) network for geographic location information associated with themobile device based on the real mobile identifier.
 12. The method ofclaim 11, wherein the geographic location information characterizes amunicipal area in which the mobile device is located.
 13. The method ofclaim 11, wherein the real mobile identifier comprises an InternationalMobile Subscriber Identity (IMSI).
 14. The method of claim 11, whereinthe real mobile identifier comprises Mobile Station InternationalSubscriber Directory Number (MSISDN).
 15. The method of claim 11 whereinthe given network node comprises a network address translation (NAT)gateway operating on a Wifi network.
 16. The method of claim 11, whereinthe given network node operates on the LTE network.
 17. The method ofclaim 11 wherein the given network node comprises a proxy server for themobile device operating on a Wifi network.
 18. A mobile InternetProtocol (IP) location server comprising one or more computers havingmachine readable instructions, the location server being configured to:provide a request to a given network node operating on a given networkfor a mobile identifier that uniquely identifies a mobile device basedon an IP address of the mobile device in response to a location requestfor the mobile device; and provide a request for location informationfor the mobile device based on the real mobile identifier for the mobiledevice to another network node operating on another network.
 19. Thelocation service of claim 18, wherein the given network comprises a Wifinetwork.
 20. The location service of claim 19, wherein the other networkcomprises a wireless carrier network.
 21. The location service of claim20, wherein the other network comprises at least one of a 3G and a LongTerm Evolution (LTE) network.